-
Notifications
You must be signed in to change notification settings - Fork 29.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert "vm: add importModuleDynamically option to compileFunction" #33364
Conversation
@SimenB this should likely fix Babel and Jest. |
I hope it can re-land later as I wanna use the code this reverts. 😀 But it does seem prudent to revert for now. |
This reverts commit 74c393d. Fixes: nodejs#33166
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rubber stamp LGTM due to revert + severity.
(Plus a non-rubber-stamp-lgtm on the delta like the md changes)
I literally have no clue on how to debug that. I know there is something in vs2019 that is affecting stdout, but it's really very hard to track. cc @ronag #32487 |
It fails also on the nightlies |
I still don't get why we consider this commit the issue and not vs2019 |
@devsnek because this commit triggers the problem. Node v14 is largely broken on one of the supported Operating Systems, and it is important that we ship a fix sooner rather than later. However I have got no clue on how to approach the vs2019 issue and it might take an unbounded amount of time to fix it. We currently have no strategy around this problem. I'm currently pinging some connections in Microsoft to see if they can help, but I fear it might take a long time to get to a conclusion as this problem is very ephemeral. |
@mcollina I mean why are we saying "build without this commit" instead of "build without vs2019". This issue could easily manifest itself in other ways (I think jasnell mentioned stream timing bugs?) so it seems like we should use a better compiler. |
I do not know how long would it take for the @nodejs/build to change the compiler we are using to build our Node.js releases. I suspect it's a significant amount of effort. I do not think we can wait fixing this bug on v14. |
I’m a bit worried here too … I get that this is a severe problem, but without understanding why this commit causes it – it almost certainly only exposes a pre-existing bug – there’s a decent chance that we’ll do some other thing that re-exposes it in the future without knowing. |
Yep. I consider this revert to be temporary to fix the acute breakage but the revert itself is not the solution. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Landed in 2d5d773 |
This reverts commit 74c393d. Fixes: #33166 PR-URL: #33364 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
This reverts commit 74c393d. Fixes: #33166 PR-URL: #33364 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
…tion"" This reverts commit 2d5d773. See: nodejs#32985 See: nodejs#33364 See: nodejs#33166 Fixes: nodejs#31860
…tion"" This reverts commit 2d5d773. See: nodejs#32985 See: nodejs#33364 See: nodejs#33166 Fixes: nodejs#31860
…tion"" This reverts commit 2d5d773. See: nodejs#32985 See: nodejs#33364 See: nodejs#33166 Fixes: nodejs#31860
This reverts commit 74c393d.
Fixes: #33166
See: #32985
See: #31860
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes